Skip to content

Fix dead Chakra UI, PublicTechnology, and Sphinx doc links - #4

Closed
olitreadwell wants to merge 3 commits into
masterfrom
docs/fix-chakra-style-props-link
Closed

Fix dead Chakra UI, PublicTechnology, and Sphinx doc links#4
olitreadwell wants to merge 3 commits into
masterfrom
docs/fix-chakra-style-props-link

Conversation

@olitreadwell

@olitreadwell olitreadwell commented Aug 12, 2026

Copy link
Copy Markdown
Owner

What this PR does

Fixes a dead link in frontend/README.md: the Chakra UI 'style props' doc link 404s.

Verification:

  • curl -sL -o /dev/null -w '%{http_code}' https://chakra-ui.com/docs/features/style-props -> 404 (chakra-ui.com restructured its docs; the old /docs/features/style-props path is gone: confirmed with a real HTTP request, not a bot-block: plain 404, no Cloudflare challenge page).
  • frontend/package.json pins @chakra-ui/react to ^2.8.2, so the canonical replacement is the version-matched v2 docs site: https://v2.chakra-ui.com/docs/styled-system/style-props -> 200, page title confirmed as "Style Props - Chakra UI".

One logical change, one line changed.

Policy passport (canada-ca/tracker)

  • default_branch: master
  • archived: false
  • CONTRIBUTING.md present (repo level); no PR template found; no CODE_OF_CONDUCT.md found
  • No org-level canada-ca/.github community-health repo (404): repo-level CONTRIBUTING is authoritative, no org defaults to merge in
  • bans_ai: false (no AI/LLM/generated-content restriction found in CONTRIBUTING, SECURITY, or .github/)
  • bans_trivial: false (no drive-by/trivial-PR restriction found)
  • ai_disclosure_required: false
  • issue_first_required: false (CONTRIBUTING asks contributors to discuss via Issues, but does not require one before opening a PR)
  • cla_required: false (no CLA bot found)
  • dco_required: false
  • signed_commits_required: false
  • fork_locked_migration: false
  • connected_ci: true (GitHub Actions workflows present in .github/workflows)
  • commit_convention: Conventional Commits, e.g. fix(dns-scanner): ..., this PR follows with docs(frontend): ...
  • recent_external_merges_60d: yes (multiple non-dependabot external merges in the last 2 weeks, e.g. PR fix(services/uptime): add custom user agent from web-scanner to avoid bot blockers canada-ca/tracker#7472, Add experimental PQC scanning support canada-ca/tracker#7470, Bump babel-jest from 30.3.0 to 30.4.1 in tracker/api canada-ca/tracker#7467)
  • policy_source: repo
  • last_checked: 2026-08-05

Fork-internal, non-draft

Base is this fork's own default branch (master), never upstream canada-ca/tracker.

AI disclosure

This PR was prepared with AI assistance (an agentic coding tool) under my direction; I will review it myself before promoting anything upstream.

No AI-use policy or disclosure checkbox was found in this repo or a would-be org default, so there is no box to leave unticked: this note is the disclosure.

Promotion (manual, not automated)

To open this against upstream once reviewed:

gh pr create --repo canada-ca/tracker --base master --head olitreadwell:docs/fix-chakra-style-props-link-20260805-004827

No CLA, no DCO sign-off, no issue-first requirement, and no signed-commit requirement were found: nothing blocks promotion as-is.

CI status

This repo's substantive test/lint/build CI runs externally on Google Cloud Build (see the gcbrun check and the northamerica-northeast1-docker.pkg.dev/track-compliance/tracker/... image tags in the commit history): not connected to forks.

The only GitHub Actions wired here are CodeQL security scanning, a Dependabot Cloud Build trigger, and a maintenance-mode toggle; none of them ran against this PR (CodeQL did not trigger on the fork).

There is no code to lint/build/test: this is a single-line markdown link fix.

Verdict: locally-verified (link checked with real curl requests, not fork-CI-green), per this project's external_ci_provider handling.


All commits in this PR

This PR bundles 3 related fixes (same repo, same trivial-fix theme: broken links / typos / stale references), per the story-PR consolidation policy:

  • docs(frontend): fix dead Chakra UI style props link
  • docs(frontend): fix dead PublicTechnology interview link
  • docs(python-client): fix dead Sphinx 3.x doc links

How to verify

git fetch https://github.com/olitreadwell/tracker.git docs/fix-chakra-style-props-link
git checkout FETCH_HEAD
curl -sL -o /dev/null -w '%{http_code}' https://chakra-ui.com/docs/features/style-props

AI assistance

Drafted with AI assistance.

The gap was found and verified against the current code, the change was verified before opening, and this diff was reviewed line by line.


PROMOTION NOTE (remove this section before/when opening against upstream):

gh pr create --repo canada-ca/tracker --base master --head olitreadwell:docs/fix-chakra-style-props-link

Prerequisites: none outstanding (re-verify CLA/DCO/signing before promoting).

@olitreadwell
olitreadwell force-pushed the docs/fix-chakra-style-props-link branch from 2d4e810 to e482b4c Compare August 18, 2026 22:43
@olitreadwell

Copy link
Copy Markdown
Owner Author

Reopening to refresh PR base against the synced fork default (removes upstream commits from the diff).

@olitreadwell olitreadwell reopened this Aug 19, 2026
@olitreadwell olitreadwell changed the title docs: fix dead Chakra UI style props link in frontend README Fix dead Chakra UI style props link in frontend README Aug 19, 2026
- The link to Chakra's style props docs 404s: chakra-ui.com
  restructured its docs site and dropped the old
  /docs/features/style-props path.
- frontend/package.json pins @chakra-ui/react to ^2.8.2, so point
  the link at the matching v2 docs site instead, where the page
  still exists (verified 200, title 'Style Props - Chakra UI').
The old URL used a percent-encoded curly-quote slug
(articles/features/interview-singapore...) that now 404s.
PublicTechnology migrated to a date-based URL scheme; the article
now lives at /2019/07/26/international-relations/... with a plain
ASCII slug. Verified the new URL returns 200 and the page title
matches the original article exactly.
The pinned Sphinx 3.x docs (index and installation instructions) have
been removed from readthedocs.org and now return a "Documentation
version not found" 404. Point both links at the master version
instead, matching the existing master-pinned link further down in the
same file (sphinx-build.html), which already resolves.
@olitreadwell
olitreadwell force-pushed the docs/fix-chakra-style-props-link branch from e482b4c to 0ec7d90 Compare August 19, 2026 00:25
@olitreadwell olitreadwell changed the title Fix dead Chakra UI style props link in frontend README Fix dead Chakra UI, PublicTechnology, and Sphinx doc links Aug 19, 2026
@olitreadwell

Copy link
Copy Markdown
Owner Author

Closing as duplicate: the same change was already submitted upstream in canada-ca#7506 (CLOSED). See canada-ca#7506

@olitreadwell

Copy link
Copy Markdown
Owner Author

Superseded by upstream canada-ca#7506.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant